docs: map Maestro compatibility debt#621
Merged
Merged
Conversation
|
Member
Author
|
Reviewed as part of the #620–#626 sweep (already merged, so just a note for follow-up). The debt map is a good anchor for the convergence work in this batch. Two additions worth folding in as the sibling PRs land, since they introduce intentional divergences that should be tracked rather than discovered later:
No change needed to the merged doc itself — just flagging the rows to extend. Generated by Claude Code |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Create a reviewer-focused Maestro compatibility debt map covering parser/mapping, runtime target matching, input/focus, assertions/waits, scroll/swipe/geometry, flow control/runFlow/retry/hooks, runScript, suite discovery, and docs/support matrix.
The table records owning files, approximate code size, custom handling, native overlap, convergence opportunities, risk, test guard status, recommendations, and suggested follow-up PR lanes.
Touched-file count: 1.
Validation
Docs-only change. Verified the committed diff with
git diff --check HEAD~1..HEAD.